Interpretability

Characteristic Name:	Interpretability
Dimension:	Usability and Interpretability
Description:	Data should be interpretable
Granularity:	Information object
Implementation Type:	Process-based approach
Characteristic Type:	Usage

Verification Metric:

The number of tasks failed or under performed due to the lack of interpretability of data

The number of complaints received due to the lack of interpretability of data

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines:	Scenario:
Standardise the interpretation process by clearly stating the criteria for interpreting results so that an interpretation on one dataset is reproducible	(1) 10% drop in production efficiency is a severe decline which needs quick remedial actions
Facilitate the interaction process based on users' task at hand	(1) A traffic light system to indicate the efficiency of a production line to the workers, a detail efficiency report to the production manage, a concise efficiency report for production line supervisors
Design the structure of information in such a way that further format conversions are not necessary for interpretations.	(1) A rating scale of (poor good excellent ) is better than (1,2,3) for rate a service level
Ensure that information is consistent between units of analysis (organisations, geographical areas, populations in concern etc.) and over time, allowing comparisons to be made.	(1) Number of doctors per person is used to compare the health facilities between regions. (2) Same populations are used over the time to analyse the epidemic growths over the tim
Use appropriate visualisation tools to facilitate interpretation of data through comparisons and contrasts	(1) Usage of tree maps , Usage of bar charts, Usage of line graphs

Validation Metric:

How mature is the process to maintain the interpretability of data

These are examples of how the characteristic might occur in a database.

Example:	Source:
when an analyst has data with freshness metric equals to 0, does it mean to have fresh data at hand? What about freshness equals to 10 (suppose, we do not stick to the notion proposed in [23])? Is it even fresher? Similar issues may arise with the notion of age: e.g., with age A(e) = 0, we cannot undoubtedly speak about positive or negative data characteristic because of a semantic meaning of “age” that mostly corresponds to a neutral notion of “period of time”	O. Chayka, T. Palpanas, and P. Bouquet, “Defining and Measuring Data-Driven Quality Dimension of Staleness”, Trento: University of Trento, Technical Report # DISI-12-016, 2012.
Consider a database containing orders from customers. A practice for handling complaints and returns is to create an “adjustment” order for backing out the original order and then writing a new order for the corrected information if applicable. This procedure assigns new order numbers to the adjustment and replacement orders. For the accounting department, this is a high-quality database. All of the numbers come out in the wash. For a business analyst trying to determine trends in growth of orders by region, this is a poor-quality database. If the business analyst assumes that each order number represents a distinct order, his analysis will be all wrong. Someone needs to explain the practice and the methods necessary to unravel the data to get to the real numbers (if that is even possible after the fact).	J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

Example:

Source:

when an analyst has data with freshness metric equals to 0, does it mean to have fresh data at hand? What about freshness equals to 10 (suppose, we do not stick to the notion proposed in [23])? Is it even fresher? Similar issues may arise with the notion of age: e.g., with age A(e) = 0, we cannot undoubtedly speak about positive or negative data characteristic because of a semantic meaning of “age” that mostly corresponds to a neutral notion of “period of time”

O. Chayka, T. Palpanas, and P. Bouquet, “Defining and Measuring Data-Driven Quality Dimension of Staleness”, Trento: University of Trento, Technical Report # DISI-12-016, 2012.

Consider a database containing orders from customers. A practice for handling complaints and returns is to create an “adjustment” order for backing out the original order and then writing a new order for the corrected information if applicable. This procedure assigns new order numbers to the adjustment and replacement orders. For the accounting department, this is a high-quality database. All of the numbers come out in the wash. For a business analyst trying to determine trends in growth of orders by region, this is a poor-quality database. If the business analyst assumes that each order number represents a distinct order, his analysis will be all wrong. Someone needs to explain the practice and the methods necessary to unravel the data to get to the real numbers (if that is even possible after the fact).

J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition:	Source:
Comparability of data refers to the extent to which data is consistent between organisations and over time allowing comparisons to be made. This includes using equivalent reporting periods.	HIQA 2011. International Review of Data Quality Health Information and Quality Authority (HIQA), Ireland. http://www.hiqa.ie/press-release/2011-04-28-international-review-data-quality.
Data is not ambiguous if it allows only one interpretation – anti-example: Song.composer = ‘Johann Strauss’ (father or son?).	KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published.
Comparability aims at measuring the impact of differences in applied statistical concepts and measurement tools/procedures when statistics are compared between geographical areas, non-geographical domains, or over time.	LYON, M. 2008. Assessing Data Quality , Monetary and Financial Statistics. Bank of England. http://www.bankofengland.co.uk/ statistics/Documents/ms/articles/art1mar08.pdf.
The most important quality characteristic of a format is its appropriateness. One format is more appropriate than another if it is better suited to users’ needs. The appropriateness of the format depends upon two factors: user and medium used. Both are of crucial importance. The abilities of human users and computers to understand data in different formats are vastly different. For example, the human eye is not very good at interpreting some positional formats, such as bar codes, although optical scanning devices are. On the other hand, humans can assimilate much data from a graph, a format that is relatively hard for a computer to interpret. Appropriateness is related to the second quality dimension, interpretability.	REDMAN, T. C. 1997. Data quality for the information age, Artech House, Inc.

Completeness of records

Characteristic Name:	Completeness of records
Dimension:	Completeness
Description:	Every real world entity instance, that is relevant for the organization can be found in the data
Granularity:	Record
Implementation Type:	Process-based approach
Characteristic Type:	Usage

Verification Metric:

The number of tasks failed or under performed due to missing records

The number of complaints received due to missing records

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines:	Scenario:
Implement a process level validation mechanism to avoid occurrence of missing records	(1) A buyer must record/verify an expense or asset in accordance with accepting/receiving any purchased items. (2)New application are stored in a temporary cabinet after entering into the system and they will be transferred to the file cabinet at the end of every week after the property manager cross check them with the system
Execute database commits upon transaction sequences in application programs and make sure all the transactions in the sequence successfully commit and generate the required records at the end of the sequence.	(1) In generating the MRP, the database operations will not be committed unless all materials in BOM is successfully executed for MRP
When distributed databases are used or online data collection devices are used, ensure the synchronisation/replication of records happen successfully without distortions and omissions.	(1) EFTPOS transactions are replicated with bank database and create the new balance B/F in the account
Implement periodic audit process for critical tangible objects that are recorded as data in database	(1) Annual audit for tangible assets in the organisation
Implement a validation mechanism in data transfers considering the business rules to monitor and ensure all records relevant to a event/transaction is transferred successfully.	(1) Rules to verify the number of records in the source file and destination file (2) All records relevant to a customer trip is transferred to the central database from online data stores
Maintain error logs for system transactions and regularly monitor them and perform relevant forensic activities to find missing records.	(1) A failed sales order creation

Validation Metric:

How mature is the process to prevent missing records

These are examples of how the characteristic might occur in a database.

Example:	Source:
if Dept is a relation representing the employees of a given department, and one speciﬁc employee of the department is not represented as a tuple of Dept, then the tuple corresponding to the missing employee is in ref(Dept),and ref(Dept) diﬀers from Dept in exactly that tuple.	C. Batini and M, Scannapieco, “Data Quality: Concepts, Methodologies, and Techniques”, Springer, 2006.
if a column should contain at least one occurrence of all 50 states, but the column contains only 43 states, then the population is incomplete.	Y. Lee, et al., “Journey to Data Quality”, Massachusetts Institute of Technology, 2006.
the database should contain all customers in North and South America, but it is known that the database reflects only a portion of the company’s customers. Coverage in this example is the percent- age of customers actually captured in the database compared to the population of all customers that should be in it.	D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition:	Source:
A record exists for every Real-World Object or Event the Enterprise needs to know about.	ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
Completeness of data refers to the extent to which the data collected matches the data set that was developed to describe a specific entity. Monitoring for incomplete lists of eligible records or missing data items will identify data quality problems.	HIQA 2011. International Review of Data Quality Health Information and Quality Authority (HIQA), Ireland. http://www.hiqa.ie/press-release/2011-04-28-international-review-data-quality.
Quality of having all data that existed in the possession of the sender at time the data message was created.	ISO 2012. ISO 8000-2 Data Quality-Part 2-Vocabulary. ISO.
Data is complete if no piece of information is missing – anti-example: "The Beatles were John Lennon, George Harrison and Ringo Starr"	KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published.
Every real-world phenomenon is represented.	PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a.